Internet Info 1994 March/Internet Info CD-ROM (Walnut Creek) (March 1994).iso/inet/ietf/hubmib/hubmib-minutes-91jul.txt

Text File | 1993-02-17 | 5KB | 141 lines

CURRENT_MEETING_REPORT_


Reported by Keith McCloghrie/Hughes LAN Systems

IEEE 802.3 Hub MIB Minutes

Since this was the first meeting of the Hub MIB Working Group, the first
item of business was discussion of the Working Group's charter.  The
discussion emphasised that the focus would be on development of a
Repeater MIB. The possibility of writing a MIB to represent a modular
chassis containing multiple repeaters/bridges/terminal-servers/etc.  was
seen as a potential future work item, depending on the wishes of the NM
Area Director and the Working-Group members, but any such effort would
take second place to the development of the Repeater MIB.

Donna McMaster then gave an overview of how an initial draft of a
Repeater MIB had been produced as a literal translation from the work of
the IEEE Hub Management Task Force's MIB. This draft and a set of
proposed changes had been distributed on the mailing-list.  Some of
these had been accepted, and some had been the subject of questions
and/or differing views.  Thus, a new draft had been produced having one
section (section 7) documenting its differences from the IEEE MIB, and
another (section 8) documenting the outstanding issues.  This draft had
also been distributed to the mailing-list, and submitted as an Internet
Draft.

After a review of the changes made so far, the Working-Group approved
the consensus reached on the mailing-list in agreeing to these changes.
A suggestion was also made to change the names of SelfTest1 and
SelfTest2 to be more descriptive of their function, i.e., non-disruptive
and disruptive, respectively.

The next item on the agenda was discussion of the outstanding issues.
The discussion began with the most fundamental issue:  whether or not
the MIB should explicitly allow for an agent managing multiple
repeaters.  Various arguments were made for each side of the argument.
Much of the discussion was intertwined with discussion of how to manage
a chassis containing multiple cards (repeaters, bridges, etc.)  and
having multiple (separate) LAN segments on its backplane.

Arguments for defining a MIB to manage just one repeater:


   o The simple agent is simpler,

   o Multiple repeaters can be managed through multiple MIB views,
     through proxy, or through multiple agents.

   o A single repeater doesn't necessarily (usually?)  correspond to an
     individual card.

   o For consistency with the Bridge-MIB, which manages only one Bridge.

                                   1





Arguments for defining a MIB with the explicit ability to manage
multiple repeaters:


   o An agent which manages multiple repeaters is simpler.
   o A single repeater doesn't necessarily correspond to an individual
     card.
   o Consistent with MIB-II's interfaces group.


After much discussion, a straw poll has called and resulted in a 15-15
tie.  Regretfully, the meeting decided that the Working-Group would have
to try to resolve the issue on the mailing-list, and if that failed then
to schedule a meeting in the September/October timeframe, possibly at
Interop.

The issue of optional tables was also discussed, and the consensus was
that the distinction between the basic and monitoring groups should be
maintained.

At this point, the meeting ran out of time, and it was agreed to take up
the discussion of the remaining issues on the mailing-list.

Attendees

Steve Bostock            [e-mail]
Howard Brown             [e-mail]
Jeffrey Case             [e-mail]
John Cook                [e-mail]
Dave Cullerot            [e-mail]
James Davin              [e-mail]
Gary Ellis               [e-mail]
Mike Erlinger            [e-mail]
Bill Fardy               [e-mail]
Jeff Fried               [e-mail]
Shawn Gallagher          [e-mail]
Phillip Hasse            [e-mail]
Mark Hoerth              [e-mail]
Ron Jacoby               [e-mail]
Mike Janson              [e-mail]
Ken Jones                konkord![e-mail]
Frank Kastenholz         [e-mail]
Manu Kaycee              [e-mail]
Mark Kerestes            att!alux2![e-mail]
Kenneth Key              [e-mail]
Cheryl Krupczak          [e-mail]
Chao-Yu Liang            [e-mail]
Keith McCloghrie         [e-mail]
Evan McGinnis            [e-mail]
Donna McMaster           [e-mail]
Lynn Monsanto            [e-mail]
David Perkins            [e-mail]
Jason Perreault          [e-mail]
John Pickens             [e-mail]

                                   2





Anil Rijsinghani         [e-mail]
Jonathan Saperia         [e-mail]
Mark Schaefer            [e-mail]
Anil Singhal             [e-mail]
Bob Stewart              [e-mail]
Emil Sturniolo           [e-mail]
Bruce Taber              [e-mail]
Geoffrey Thompson        [e-mail]
Dean Throop              [e-mail]
Steven Waldbusser        [e-mail]
Philip C. Wang           watadn![e-mail]
Drew Wansley             [e-mail]
David Ward               [e-mail]
Joseph Zur               fibrontics![e-mail]



                                   3